The One-On-One That Turned Into A Status Meeting

Dan opens his laptop and pulls up the board. Sofia joins on time, as always.

They go ticket by ticket. The API work is blocked on the vendor. The reporting change went out Tuesday. The onboarding bug is in review. Dan asks about the timeline on the second one. Sofia says Friday, probably Monday. He nods and types something.

At 2:26 he asks if there's anything else. Sofia says, "No, all good, thanks." They both leave four minutes early, which feels efficient.

Every fact exchanged in that meeting was already in Slack, in the board, or in Tuesday's standup notes.

Eleven weeks later Sofia resigned. In her exit conversation she said she had been thinking about leaving since February. Dan and Sofia had met every Thursday, without fail, throughout February.

What was actually going on in that room

The meeting was doing something. It was just doing the wrong thing efficiently.

Steven Rogelberg has spent years studying these meetings specifically, and his conclusion in Harvard Business Review is blunt about the design flaw: one-on-ones work when the conversation is dominated by what matters to the direct report, and they fail when the manager's own concerns set the agenda. His research also found that managers who run these badly leave their people disconnected both functionally and emotionally, which is a fair description of somebody who says "all good" for eleven weeks and then hands in a letter.

His article opens on a manager he calls Bill, whose team had higher turnover than almost any other in his company. Bill thought of himself as a good manager. The exit interviews said his departing people had never felt meaningfully engaged.

Sofia's Thursdays were not neglect. Dan showed up every week, on time, prepared, with the board open. The preparation was the problem, because a manager who arrives with the ticket list has already decided what the half hour is for.

The pattern underneath

Status is easy, and the other thing is hard.

Talking about the API blocker is safe, factual, and finishable. Asking Sofia whether she can see herself here in two years is none of those things, and it opens a conversation Dan cannot close in the remaining eleven minutes.

So the meeting drifts to the material that fits the container. Every week the drift is reasonable. After six months the meeting has a genre, and the genre teaches Sofia what to bring. She stops preparing anything that doesn't look like a ticket, because the last three times she started to raise something bigger, the clock and the board were both in the way.

The signal that this has happened to you is the "all good" at the end. A person who has been given thirty minutes and produces nothing beyond the board is telling you what the meeting is for, and they learned it from you.

Try this on Monday

• Hand over the agenda in writing. Send one message: from now on these are yours, bring me two or three things you want to talk about, and I'll come with one. Rogelberg's survey work found weekly meetings of around 30 minutes were what employees across job levels most wanted, so the slot is probably fine. The ownership is what changes.
• Open with a question that cannot be answered with a status. "What's on your mind that we won't cover in standup?" works. So does "what's been taking the most out of you lately?" Ask it, then stop talking. The first silence will run about eight seconds and you must let it.
• Move the status somewhere else out loud. Say the sentence: I can get the ticket updates from the board, so let's not spend Thursday on them. Without that sentence your report will assume the updates are still expected and will keep preparing them.

Count who talked. At the end, estimate the split. If you spoke for more than a third of a meeting that belongs to them, that's the number to fix next week, and it's the easiest thing on this list to measure.

Where this goes wrong

Now, this can go wrong in a lot of ways. It’s best you are prepped for the worst.

• Announcing the change to one person. Do it with the whole team in the same week or the one person will spend a fortnight wondering what they did.
• Filling the silence. Eight seconds feels like a minute. Rephrasing the question at second four is how the meeting reverts to the board, because the board is what's available.
• Turning it into an interrogation about feelings. "What's on your mind" is an invitation. "Are you happy here?" asked in month one of a new format is a demand for disclosure that the relationship hasn't earned yet.
• Asking for feedback about yourself, getting nothing, and never asking again. Silence the first time is the expected result. Ask three times before you conclude anything.
• Cancelling when the week gets bad. The week when you most want to cancel is the week they most needed it, and cancelling teaches them where the meeting sits in your ranking.

One thing this week

Send the message before your next one-on-one. Two sentences, no meeting required: this half hour is yours; bring two things.

Dan sent it to four people on a Monday. His next Thursday was awkward. Sofia's replacement brought one item, ran out of things to say after nine minutes, and they sat in it. The Thursday after that she brought three, and the third one was about whether the team was heading somewhere she wanted to go.

That third item is the meeting. Everything else is a board you could have read on your phone.